I'm not sure that this would work... the copy will be instantiated with null values on those fields anyway, so not sure this actually defends against anything?

I'm not sure that this would work... the copy will be instantiated with null values on those fields anyway, so not sure this actually defends against anything?

I just feel that it is possible the prereqs could have been populated by a different instrumentation point and the risk is that a valid value stored on the instance could be replaced by a later set call that adds a null. There are a couple of other instrumentation points that set prereqs values.

I can't see any intervention pathway where that would be possible, short of constructor advice pulling it from context.. and then how do you get it into the constructor context if not here?

I'm gonna close this, I think it's the wrong approach